home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
remote
/
ramail30.zip
/
RAMAIL.DOC
< prev
next >
Wrap
Text File
|
1991-08-01
|
21KB
|
459 lines
▒██████ ▒██████ ▒██ ▒██ ▒██
▒██ ▒██ ▒██ ▒██ ▒███ ▒███ ▒█████ ▒██ ▒██
▒██████ ▒██████ ▒████▒████ ▒██ ▒██
▒██ ▒█ ▒██ ▒██ ▒██▒███▒██ ▒█████ ▒██ ▒██
▒██ ▒██ ▒██ ▒██ ▒██ ▒█ ▒██ ▒██▒██ ▒██ ▒██
▒██ ▒██ ▒██ ▒██ ▒██ ▒██ ▒██████ ▒██ ▒██
Release 3.0
Copyright 1990, 1991 by Randy Blackmond
All Rights Reserved
Page 1 RAMail v3.0
──────────────────────────────────────────────────────────────────────────
Welcome to RAMail, the mail system exclusively for RemoteAccess!
This version will probably not work with any RA versions prior to 1.01.
FILES INCLUDED IN THE RAMAIL30 ARCHIVE
──────────────────────────────────────
RAMAIL.DOC - The main documentation (this file)
RAMCONF.DOC - The documentation for the config program, RAMCONF.EXE
RAMUSRED.DOC - The documentation for the RAUSER.DAT editor
NEWRAU.DOC - The documentation for the NEWRAU conversion utilities
NEWRAU18.EXE - The RAUSER.DAT conversion utility for Beta 10 thru 17
NEWRAU30.EXE - The RAUSER.DAT conversion utility for Beta 18
RAMAIL.EXE - The executable door program
RAMCONF.EXE - The executable configuration program
RAMUSRED.EXE - The executable RAUSER.DAT editor
RAMWELC.ASC - Sample ASCII welcome file
RAMWELC.ANS - Sample ANSI welcome file
RAMMENU.ASC - Sample ASCII menu file
RAMMENU.ANS - Sample ANSI menu file
RAMAIL.HLP - Online Help file
DOOR.ID - Door identifier used by SLMR and possibly other readers
BETATEST.APP - Beta Tester application for future versions of RAMail
THE READER
──────────
The RAMail Door is only half of the complete system. The other half
is a reader. You, as a sysop, don't need a reader for your door to
function, but your users will so they can read and reply to the mail
in the packets the door produces. I recommend The Silly Little Mail
Reader, but Session Manager, Qmail or EZ-Reader will also work.
INSTALLATION
────────────
The first thing you need to do is to create a RAMAIL.CFG file by running
the RAMCONF.EXE program. You must supply the name of the CFG file you wish
to create/edit on the command line with RAMCONF, e.g. RAMAIL RAMAIL.CFG
The fields are described in RAMCONF.DOC.
EXTERNAL SUPPORT FILES
──────────────────────
Except where noted, all files listed below use the ASC/ANS extension
convention for BBS display files and must reside in your RA TextFiles
directory. All are optional except where noted.
RAMWELC.A* - This file is displayed to the user upon entering the door.
RANEWUSR.A* - This file is displayed to a user after the welcome screen
the first time he enters the door.
RAMNEWS.A* - This file is displayed to all users after the opening
welcome screen.
RAMMENU.A* - The RAMail menu. These files are REQUIRED.
RAMAIL.HLP - This file is REQUIRED and must reside in the same
directory as RAMAIL.EXE.
Page 2 RAMail v3.0
──────────────────────────────────────────────────────────────────────────
HELLO.A* - This file is included in the users' packets for display
by the reader. If not found, your WELCOME.A* file will
be used.
INFO.A* - This file is included in the users' packets for display
by the reader. If not found, your NEWS.A* file will be
used.
BYE.A* - This file is included in the users' packets for display
by the reader. If not found, your GOODBYE.A* file will
be used.
All external display files used by RAMail support some of the more common
control codes used by RA. These include clear screen, pause, user name and
others. Attempts to use an unsupported code will result in N/A being dis-
played. See RA.DOC for an explanation of these codes.
Code 7 Setup
────────────
Put RAMAIL.EXE, RAMAIL.CFG, RAMAIL.HLP and DOOR.ID in your RA system
directory. The menu entry for RAMail should be as follows:
Optional Data: RAMAIL.EXE RAMAIL.CFG *M
You should use RA's swapping to ensure there is enough memory for RAMail
to run. To do this put *M after RAMAIL.EXE RAMAIL.CFG on your Optional
Data line. Failure to do so will probably result in not enough memory
being available for RAMail to run.
Code 15 Setup
─────────────
First, create a directory on your hard drive in which RAMail will reside.
Place RAMAIL.EXE, RAMAIL.CFG, RAMAIL.HLP and DOOR.ID into that directory.
Create a batch file like the one below:
@echo off
cd \RA\RAMAIL
RAMAIL RAMAIL.CFG
cd \RA
Note that the name of the CFG file you created is passed to RAMAIL.EXE on
the command line. Also, ANSI.SYS or some facsimile must be loaded to
enable you to see the ANSI colors the door uses locally. Loading ANSI.SYS
is not necessary for successful operation of the door, however.
Place the batch file in your RA directory and add the door to your menu
the same way you add any level 15 door.
There is a file included with the RAMail package named DOOR.ID. This file
is used by SLMR to determine which mail door created the packets. Simply
place the file in the same directory as RAMAIL.EXE and RAMail will include
it in all QWK packets automatically.
Page 3 RAMail v3.0
──────────────────────────────────────────────────────────────────────────
USAGE
─────
The menu for RAMail is straightforward. The options are: Conference
Select, Download, Upload, File Areas, Page, System Info, Bulletin Toggle,
Transfer Protocol, Help, New Files, Express Mail Run, Include New Files
Toggle, ANSI Toggle, Packing Method, Restore Pointers, Modify Pointers,
Quit and Goodbye.
Conference Selection allows your users to decide which message boards they
wish to be included in their downloaded mail. It will display all avail-
able message boards and allow them to pick which ones they want. The con-
figuration the user chooses will be saved in a mini user file maintained
by RAMail. They can change their configuration at any time. Users will
not be allowed to choose boards for which they do not have a high enough
security level and/or a set Read Flag to read.
The Download option extracts all new mail for the configuration the user
has chosen and places them in a compressed packet and then invokes a send
of the packet.
The Upload option invokes reception of a reply packet that will be named
[BBSCODE].REP. It will then uncompress the packet and import the replies
to your message files where they will be available immediately for
reading.
The File Areas option allows users to view your file lists and flag files
to be downloaded with their mail packet. Checking is done to ensure the
user has access to a given file area according to security level and flag
settings. Full support of LIMITS.CTL is provided automatically as well.
The maximum number of files a user can flag for download is 5. This option
can be disabled in RAMCONF.
The Page option allows the user to page the Sysop for a chat. This option
can be disabled in RAMCONF.
The System Info option displays message stats, total calls and last caller
information. This option can be disabled in RAMCONF.
The Bulletin Toggle allows the user to enable/disable the inclusion of
new bulletins in his/her mail packet.
The Transfer Protocol option allows the user to select a download protocol
to be used when performing mail/file transfers. This option is initially
set to Zmodem for new users.
The Help option will display the file RAMAIL.HLP. You can use the included
file or create your own. RAMAIL.HLP must reside in the same directory as
RAMAIL.EXE.
The New Files option will search all available file directories for files
newer than (or equal to) the date of the user's last call and list them to
the screen. This option can be disabled in RAMCONF.
The Express Mail Run option will cause RAMail to create the mail packet
and then immediately send it. Upon completion of the transfer, the user
will be logged off.
Page 4 RAMail v3.0
──────────────────────────────────────────────────────────────────────────
The Include New Files Toggle option enables/disables the new files scan
that RAMail performs during packet creation.
The ANSI Toggle allows the user to turn ANSI off and on. Any change
made remains effective only while in the RAMail door.
The Packing Method option allows the user to choose which of the 3
compression methods that you have configured to be used when processing
mail packets.
The Modify Pointer option allows the user to set ALL Last Read Pointers
simultaneously to a new value.
The Restore Pointers option restores a user's pointers to the state they
were in before the user's previous download. Note that if you renumber
your messages, the saved pointers will then be invalid until the user
downloads his next packet. The purpose of this option is to allow the
user to recover from trashed packets due to things such as CRC errors and
corrupt files.
The Quit option returns the user to the BBS.
The Goodbye option disconnects the caller and exits the door.
Users can select the board configuration they want by entering special
offline messages. If a message is addressed to RAMAIL or QMAIL the
subject will determine the configuration action to be taken. The choices
for the subject are as follows:
ADD - Adds a conference and selects all mail
ADD A - Adds a conference and selects all mail
ADD Y - Adds a conference and selects your mail only
ADD YA - Adds a conference and selects your mail and mail to All
DROP - Drops a conference
Selecting to receive your own messages can currently only be done online.
Netmail messages can be entered by placing NET> followed immediately by
the zone:net/node address on the first line of the message, e.g.
NET>1:381/70
The message board that the message is imported to must be a NetMail board.
HISTORY
───────
1.0 Initial release of RAMail!
1.1 Increased the speed of the message export process TREMENDOUSLY!
200 message packets should be created in about 30 seconds or so.
Did away with the idea of conference pointers. There's just no
feasible way to do something like that with RA. The last read
message pointer will be read from the user's record upon entry
into RAMail and updated after downloading a packet.
1.2 This version was released as a fix for the problem of the last read
message pointer not being updated. Too bad it didn't fix it!
Page 5 RAMail v3.0
──────────────────────────────────────────────────────────────────────────
1.3 Discovered reason for the read pointer not being updated (I thought)
Added different message download limits for each baud rate (See
INSTALLATION). Added Hot Keys.
1.4 Finally! An enhancement version! The Configuration option has been
enhanced to allow the user to elect to receive only their mail and
mail addressed to All or All mail. Added the Modify Last Read
Pointer option. Added optional RACONFS.LST board name file. Last
Read Message Pointer problem was finally solved!
1.5 Stomped a few more bugs. Added FIDO Default Origin line support for
messages uploaded to an EchoMail board. Increased packet processing
speed even more. RA's message indexes are automatically updated by
RAMail when replies are uploaded. New RAMCONF program eases creation
and modification of your RAMAIL.CFG file(s). Added support for
multiple nodes. RAMail should now work properly on boards where the
message files reside in their own directory. Much more!
2.0 Still more bugs stomped. Should now be completely FIDO compatible.
Added Files feature, Your Mail Only mail selector, high ASCII filter
option for FIDO boards, Personal Mail support, New Files and New
Bulletins support, Default Protocol, Online Help, Goodbye from the
menu or after transfer and more!
2.01 Maintenance release. The message attributes set by RAMail were all
messed up resulting in such problems as imported EchoMail messages
not being marked as pending export and private messages not being
marked or recognized as private.
2.1 Added path for RAUSER.DAT in RAMCONF.EXE. This was to allow multiple
node systems to use the same RAUSER.DAT file for all nodes. Added
(S)elect All and (D)eselect All in the configuration option.
2.2 Added support for the DOOR.ID file that SLMR 2.0 will make use of.
Added offline mail configuration support. RAMail will write to your
system log(s) when mail/files are download/uploaded. Origin lines
are attached to incoming echo mail only if Echo Info is enabled in
your RACONFIG. Stomped a few bugs.
3.0 Netmail support added. Reader taglines in Echomail and Netmail
boards can be stripped. Several menu options can now be turned off
if desired. Several external display screens have been implemented.
Compression/decompression and protocol programs are now fully
configurable. A new page-oriented conference select screen is now
used. Users can select to receive their own messages on a per
conference basis when in C)onference Select. And MORE!
DISCLAIMER
──────────
As stated before, all reasonable precautions have been take to ensure
that your system files will not be damaged, but if any damage does
occur caused by RAMail either directly or indirectly, I will not
be held responsible for such damages. USE THIS PRODUCT AT YOUR OWN RISK!
Page 6 RAMail v3.0
──────────────────────────────────────────────────────────────────────────
CREDITS
───────
This Door was written with JPDOOR 3.1 Copyright 1991 by Rod Hancock
PKZIP/PKUNZIP is Copyright 1989-1991 by PKWARE, Inc.
LHA is Copyright 1988-1991 by Haruyasu Yoshizaki
ARJ is Copyright 1990, 1991 by Robert K. Jung
DSZ is Copyright 1991 by Omen Technology INC
QuickBBS is Copyright 1990 by The QuickBBS Group, Inc.
RemoteAccess is Copyright 1991 by Continental Software
Session Manager is copyright 1991 by Patrick Hart
EZ-Reader is copyright 1988-1991 by Thumper Technologies
Qmail is copyright 1987-1991 by Sparkware
Silly Little Mail Reader is copyright 1991 by Greg Hewgill and
Computer Techniques
And special thanks to the beta testers for their patience, support and
wonderful suggestions!
PROBLEMS & SUGGESTIONS
──────────────────────
Bug reports, problems, suggestions and comments can be made to Randy
Blackmond in the RIME/RelayNet Doors, Sysops, Shareware or RA conference,
The FIDONet Doors, Shareware or RA Utilities echos, NetMail to 1:381/70 or
call Randy's Basement BBS 1200/2400/9600 USR DS at (505) 589-0319. I can
also be reached voice at 505-589-0317. I STRONGLY encourage users to give
suggestions for new features they would like to see implemented!
COMMON ERROR CODES:
2 File Not Found
Check all paths in your RAMail configuration.
3 Path Not Found
Check all paths in your RAMail configuration.
100 Disk Read Error
This can result if you have an invalid RAUSER.DAT or
invalid RAMAIL.CFG file. Delete one or both and start over.
Will also occur if you are running a version of RA prior
to 1.01. You MUST be running RA 1.01!
101 Disk Write Error
Results from a full disk. Free some disk space.
COMMON PROBLEMS AND SOLUTIONS
─────────────────────────────
Problem: File transfers are always reported as aborted!
Solution: Set your DSZLOG environment variable (see DSZ.DOC).
Problem: After an uploaded reply packet has been received, RAMail
locks up!
Solution: You must have your RA environment variable set!
Page 7 RAMail v3.0
──────────────────────────────────────────────────────────────────────────
Problem: RAMail does not run on my system AT ALL!
Solution: You do not have enough memory for RAMail to run in. Add the
*M on your Optional Data line if you are using a type 7
setup. If you are using a type 15 setup and still have this
problem, you either have too many TSRs loaded or you are
running in too small of a multitasking window.
Problem: The mail packets are created fine, but when the transfer
procedure begins, it always aborts.
Solution: You probably have an error in your protocol definition in
your RAMail configuration. Unless you REALLY know what you
are doing, you should use the DSZ defaults provided by
RAMCONF.
Problem: A user who uses Session Manager complains of messages being
listed in the wrong conference.
Solution: Session Manager has some problem with RAMail packets. To
resolve it, when loading SM, do it in this manner:
SM /FI /TC
REGISTRATION
────────────
Usage of the RAMail Door for longer than a 2 week evaluation period
requires that you register the product with the author. Failure to do
so violates Federal Copyright Laws and places you in a position to which
the author can pursue monetary damages in a court of law. Why risk it?
Register the software. Registration entitles you to free upgrades forever.
To register the RAMail Door, you have two options. 1) Complete the
following form and mail it back to the author with a check or money order
made payable to Randy Blackmond for $25.00. 2) Call my board and register
with your Visa or MasterCard. Your registration number will be left for
you in a private message on my board. You will need to call and establish
a user account for this purpose. If you are in FIDONet and accept
crashmail, I will send the number to you via NetMail.
──────────────────────────────────────────────────────────────────────────
Randy Blackmond
RR #1 Box 634 RAMail 3.0 Door Registration Form
Anthony, NM 88021
NAME: _______________________________ ADDRESS: ________________________
CITY, STATE, ZIP CODE : ________________________________________________
HOME VOICE PHONE: _____________________ BBS NAME: ______________________
BBS PHONE: _____________________ BAUD RATES SUPPORTED: _________________
ARE YOU IN FIDO? IF SO, YOUR NET/NODE ADDRESS: _________________________
COMMENTS: ______________________________________________________________
________________________________________________________________________
________________________________________________________________________